Conversation
…rterly tier - backup_policy.py: add quarterly schedule (1st of Jan/Apr/Jul/Oct at 06:00), change retention defaults from 7/4/2 to 1/1/1/1 (one snapshot per tier), rename schedule names from "daily-7" etc. to plain "daily"/"weekly"/"monthly"/"quarterly" - cli.py: auto-apply DLM policy at end of `edc provision` (warn on failure); show backup policy state in `edc status`; warn before `edc destroy` if no active policy is found; add --quarterly-keep option to `backup-policy apply` - tests: update defaults throughout; add test asserting quarterly schedule is included and that 4 schedules are created - docs/ARCHITECTURE.md: document auto-apply behaviour, retention tiers, and instance-state independence Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
edc provisionnow callsbackup-policy applyautomatically after the instance is created. Failure is non-fatal (warns and continues).edc statusnow shows backup policy ID and state (ENABLED/DISABLED/absent).edc destroywarns to stderr if no active DLM policy is found before proceeding.Test plan
edc provisionoutput includes "DLM backup policy active" lineedc statusshows "Backups: DLM policy ..." lineedc destroy(with no policy) prints backup warning to stderredc backup-policy applyaccepts--quarterly-keepoptiontests/test_backup_policy.py,tests/test_cli.py)🤖 Generated with Claude Code